Fixed incorrect json representation of ResourceType in PermissionRepresentation #296
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…esentation ResourceType in PermissionRepresentation should be formatted as lower camel case instead of snake case
|
Hi thanks for your contribution, now merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ResourceType in PermissionRepresentation should be formatted as lower camel case instead of snake case
Attempting to create a resource based policy that is restricted to a resource type, will result in an unknown_error along with the following error in the keycloak log:
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "resource_type"